Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Batch object migration

This utility generates dynamic versions of specified static objects, including SmartBusinessObjects. It works on the same principle as the File> Save as Dynamic Object option, except it is done for a selected and filtered group of objects. To launch it, choose the ADM to Dynamic icon from the ProTools palette. The window shown in Figure 6–2 opens.

Figure 6–2: Static SmartObject to Dynamic Object Migration Utility window

The filtering mechanism works on two levels: the physical directories and subdirectories on disk and the product modules in the Repository.

Some of the controls on the UI are explained below:

Directory — Defaults to the root directory, but you can change it.
Filter — Shows the file type, which defaults to .w.
Build/Rebuild file list — Clears and populates the list of files to migrate.
Product module — Is the product module to which the new objects will be assigned.
Repository modules — Lets you specify to include Progress Dynamics framework modules.
Register — Registers nonmigrated static objects if they are in the proper directory. If the utility determines that it cannot convert a static object to its dynamic form, it will register the object as a static object (but only if the static object already exists in the directory for the specified product module.) You should specify to register nonmigrated objects so that the Progress Dynamics framework will be aware of their existence. You must register all objects that you want to deploy.
Log file — Lets you specify a different name and relative path for the log file, which you can review and print.
Start migrations — Initiates the processing of files shown in the list. Each file is read into the AppBuilder silently (without any visualization.) If it is a SmartDataViewer, a SmartDataBrowser, or a SmartBusinessObject, it is written to the Repository. Any other file type is rejected or not converted, although all files will be registered in the Repository. A log file is kept that indicates any rejections, any errors encountered, any unusual situations, and all of the objects successfully converted. If no product module is specified, then nothing is converted and an alert box displays explaining the problem.
Advanced settings — Displays the Advanced Migration Settings window, as shown in Figure 6–3.



Figure 6–3: Advanced Migration Settings window

This Advanced Migration Settings window lets you change the naming conventions and actions of the static SmartObject to Dynamic Object Migration Utility tool. For example, you can:

Specify different Product Modules for different object classes.
Generate datalogic procedures containing all custom code sections of the original static SDO.
Generate custom super procedures containing all custom code sections of the original static SDV or SDB.
Add or remove suffixes and prefixes to or from the object name.